Chore: Automate versioning with GitHub actions#69
Merged
Conversation
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automate versioning with GitHub actions
This PR introduces a GitHub Actions workflow to automate versioning based on PR labels. It ensures that versioning is handled consistently by automatically updating the version in
CMakeLists.txt, committing the change, and tagging the new version in Git.🔍 How It Works
When you're ready to merge a PR, you add a versioning label (
version:major,version:minor, orversion:patch).This triggers the workflow, which will:
Merge
devinto the PR branch to ensure the latest version is used.Determine the new version based on the label:
version:major→1.2.3 → 2.0.0version:minor→1.2.3 → 1.3.0version:patch(default) →1.2.3 → 1.2.4Update
CMakeLists.txtwith the new version and create a commit (if necessary).Create and push a new Git tag, linking it to the latest commit.
Once the workflow completes, the PR can be merged into
dev, and the new version is tagged automatically.🔧 Changelog
actions/checkoutto version 4